Add native C++ and Python implementations - #4
Merged
Conversation
rantri
marked this pull request as ready for review
July 10, 2026 12:26
rantri
marked this pull request as draft
July 10, 2026 12:34
rantri
marked this pull request as ready for review
July 10, 2026 12:46
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Motivation
SharedMemoryStore previously exposed only the managed implementation. Keeping the C++, Python, and .NET implementations in one repository lets them share a versioned protocol contract, fixtures, and interoperability gates, reducing the risk of layout or lifecycle drift.
User and developer impact
C#, C++, and Python processes can now exchange values through the same shared-memory store on Windows and Linux. Native consumers can use either the C ABI or the CMake-exported C++ API, while Python consumers receive a normal wheel with no runtime compiler requirement.
Platform-specific mapping, locking, and packaging concerns remain behind stable protocol and ABI boundaries. Existing managed API behavior remains compatible.
Validation